Description

This PR addresses several issues related to file reading functionality and improves the user experience when working with large files and line range notifications:

Closes #3351

1. Added tooltips for truncation messages:

   • Before: When a file was truncated due to size limits, there was no tooltip on the truncation message to guide users on how to adjust this setting.
   • Fix: Added an informative tooltip to the info icon next to the truncation message, explaining how to adjust the file read auto-truncate threshold in settings.
   • Implementation: Created the necessary translation infrastructure by adding the missing tools.json files to the webview-ui directory for all supported languages, ensuring consistent translations across both components of the application.

2. Enhanced readFileTool with improved auto-truncate handling:

   • Before: The wasAutoTruncated flag was not being set correctly, leading to inconsistent UI behavior when files were truncated.
   • Fix: Improved the logic for setting the wasAutoTruncated flag to ensure it's only set when a file is actually truncated due to the maxReadFileLine setting, not when the user explicitly requests a range of lines.

3. Improved line range notifications:

   • Before: Line range notifications were only displayed in certain conditions based on the maxReadFileLine setting, leading to inconsistent UI feedback.
   • Fix: Modified the readFileTool to always display line range notifications regardless of the maxReadFileLine setting, making the UI more consistent and informative.

4. Hidden truncation messages for explicit line range reads:

   • Before: Truncation messages were shown even for explicit line range reads, which was confusing since the user had intentionally specified the range.
   • Fix: When users explicitly specify line ranges, the truncation message is now hidden since it's not relevant in those cases.

5. UI improvements:

   • Enhancement: Added a clear visual indicator (info icon) that additional information is available about file truncation.
   • Enhancement: The tooltip uses variables to reference other translations (settings, context, and threshold), ensuring consistency across the UI and all supported languages.

These changes collectively improve the user experience when working with file content in Roo, making the behavior more intuitive and the UI more informative, especially when dealing with large files or specific line ranges.

Test Procedure

Testing was performed by:

1. Verifying tooltips display correctly with proper variable substitution in all supported languages
2. Testing file reading with various configurations:
   • Large files that trigger auto-truncation
   • Files with explicit line range requests (start_line/end_line)
   • Files with different maxReadFileLine settings (0, positive values, -1 for full read)
3. Confirming line range notifications appear correctly in all scenarios
4. Running the translation verification script (node scripts/find-missing-translations.js) to ensure all translations are complete
5. Manual testing in different language settings to verify correct text display

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• ♻️ Refactor Changes
• 💅 Cosmetic Changes
• 📚 Documentation update
• 🏃 Workflow Changes

Pre-flight Checklist

• Changes are limited to a single feature, bugfix or chore (split larger changes into separate PRs)
• Tests are passing (npm test) and code is formatted and linted (npm run format && npm run lint)
• I have created a changeset using npm run changeset (required for user-facing changes)
• I have reviewed contributor guidelines

Screenshots

BEFORE:

AFTER:

Additional Notes

This PR highlights the importance of maintaining consistent translation namespaces across both the extension and webview components. For future development, we should consider adding an automated check to ensure translation namespaces remain synchronized between the two components to prevent similar issues.

The improvements to line range notifications and truncation handling make the file reading experience more intuitive and consistent for users, especially when working with large files or specific line ranges.